juliacon update #1271
juliacon update #1271
Conversation
…track Allow AEiC to change paper's track
Small type
Update paper_spec.rb
Small typo fix
Bumps [rails-html-sanitizer](https://github.com/rails/rails-html-sanitizer) from 1.4.2 to 1.4.3. - [Release notes](https://github.com/rails/rails-html-sanitizer/releases) - [Changelog](https://github.com/rails/rails-html-sanitizer/blob/master/CHANGELOG.md) - [Commits](rails/rails-html-sanitizer@v1.4.2...v1.4.3) --- updated-dependencies: - dependency-name: rails-html-sanitizer dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
…dler/rails-html-sanitizer-1.4.3 Bump rails-html-sanitizer from 1.4.2 to 1.4.3
Co-authored-by: Daniel S. Katz <[email protected]>
Co-authored-by: Daniel S. Katz <[email protected]>
…ict-policy Add conflict policy link to ethics guidelines
…analytics Updating Google Analytics tracking
…albot-docs Update the editorialbot docs
Retraction papers
security release
|
Hi Luca, here are some quick responses, I'll take a more detailed look at the PR code and go back to you.
You need to have installed Ruby 3.2.2 and have running locally elasticsearch and postgres. Then:
The value of that header string is not really important, other than to be visually informative, so is not needed to update it but to be correct I suggest you change it from
This points to a place where reviewers are managed, in JOSS we have a dedicated app, you can left it blank or use https://juliacon.github.io/proceedings-guide/reviewer/
This is the url of the place where potential reviewers can sign up, in your case I think is: https://forms.gle/Zr9jNaWg45qkAWKT6
This is a link to the list of reviewers, if you don't have a public list I guess this is enough: https://juliacon.github.io/proceedings-guide/reviewer/
Yes, heroku email addon is configured to allow that email address to send the internal emails |
@xuanxu @arfon I tried to merge main into the
juliaconand went through the conflicts. It wasnt too bad, but I assume I messed up something. Is there an easy(ish) way to deploy the website (at least as static) locally and check it looks about right?A few notes I took while going through the conflicts
the
repository.ymlfile had a renamejoss-review-testing --> joss-reviews, could you comment on which one we should use in this case?the files
settings-test.yml,settings-development.ymlandsettings-production.ymlseemed identical. I updated the metadata and marked asFIXMEthe new fields that wasnt sure how to fill. Most of them I can figure out asking juliacon people, however the following I didnt know how to setup, ideas what the correct link looks like?editor-emailandnoreply-emailwas set to[email protected](also in the old version), not sure this is correct.This is as draft for now, since we need to first assemble the gh action to compile latex, meanwhile we can start to take a look.
cc @matbesancon